-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(operator): include kubearmor installation via helm #1377
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PTAL at the suggested comments.
deployments/helm/KubeArmorOperator/templates/serviceaccount.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please add a test for kubearmor via the chart ?
75e6d8b
to
7b057ea
Compare
Please include deployments/helm in the workflow paths. Also update namespace in |
7b057ea
to
6c550d6
Compare
Addressed 👍 |
With this PR KubeArmor will be installed with default configurations with the operator by a single helm install command. Signed-off-by: Ankur Kothiwal <[email protected]>
6c550d6
to
a1a57b3
Compare
Will it work on ARM based CPU? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚀
The PR only automates the process of deploying KubeArmor from the Operator. If the Operator installation works fine on ARM then this will also work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
We have reconsidered our approach and have opted to stick with the current method of installing the operator first, followed by the kubearmorconfig CR. The reasons are:
|
With this pull request, KubeArmor will be installed with default configurations using the operator through a single Helm install command.
Purpose of PR?:
Fixes #1374
Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::
Installation verified locally on k3s.
Checklist: